Handling identifiers for enhanced dedicated channels in cell forward access channel states

ABSTRACT

A device receives information regarding allocation of an enhanced dedicated channel radio network temporary identifier (E-RNTI) to user equipment in a cell forward access channel (Cell_FACH) state, and receives information regarding a state change associated with the user equipment. The device determines that the E-RNTI can be released based on the state change, and provides, to another device, a request to release the E-RNTI in response to the state change and so that the E-RNTI can be used by other user equipment.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.14/569,052, filed Dec. 12, 2014, which itself is a continuation of U.S.patent application Ser. No. 13/748,881, filed Jan. 24, 2013, now U.S.Pat. No. 8,929,903, which itself is a continuation of U.S. patentapplication Ser. No. 12/934,053, filed Dec. 20, 2010, now U.S. Pat. No.8,380,214, which itself is a 35 U.S.C. §371 national stage applicationof PCT International Application No. PCT/SE2009/050228, filed on 5 Mar.2009, which itself claims priority to U.S. provisional patentApplication Nos. 61/040,866, filed 31 Mar. 2008 and 61/048,464, filed 28Apr. 2008, the disclosure and content of all of which are incorporatedby reference herein in their entirety. The above-referenced PCTInternational Application was published in the English language asInternational Publication No. WO 2009/123544 A1 on 8 Oct. 2009.

TECHNICAL FIELD

Embodiments described herein relate generally to wireless communicationsystems, and more particularly, to handling of enhanced dedicatedchannel (E-DCH) radio network temporary identifiers (E-RNTIs) andhigh-speed downlink shared channel (HS-DSCH) RNTIs (H-RNTIs) for userequipment in a cell forward access channel (Cell_FACH) state.

BACKGROUND

An enhanced dedicated channel (E-DCH) is used as a transport channel foruser equipment in a Cell_FACH state. The E-DCH is used for commoncontrol channel (CCCH), dedicated control channel (DCCH), and/ordedicated traffic channel (DTCH) transmissions. One CCCH message can besent at multiple transmission timing intervals (TTIs) so thatre-ordering is needed. On the E-DCH channel temporarily granted toparticular user equipment, the data packets are set to the network.There are control channels in the downlink direction used to control thegranting of resources to the user equipment. The user equipmentrecognizes which control messages that are relevant by the E-DCH RadioNetwork Temporary Identifier (E-RNTI). The E-RNTI is allocated by a basestation (or Node B) when the user equipment establishes an E-DCH, and isunique within a cell carrying the E-DCH. The E-RNTI may be included in amedia access control (MAC) header when the user equipment accesses theE-DCH common channel. An E-DCH absolute grant channel (AGCH) with theE-RNTI is used for contention resolution. No contention resolution isperformed for CCCH.

The E-RNTI allocated to the user equipment has to be unique within thecell among all of the user equipment that are using the E-DCH (i.e., theuser equipment that are in the Cell_FACH state and the user equipmentthat are in the Cell_DCH state).

For the enhanced Cell_FACH in the uplink, MAC-i and MAC-is are used tosupport the E-DCH transmission in the Cell_FACH state. One MAC-is entityper user equipment is located in the serving radio network controller(RNC) for handling DCCH/DTCH transmissions in the Cell_FACH state forthe E-DCH. The MAC-is for CCCH is located in the controlling RNC.

For the downlink, Cell_FACH users may also use a high-speed packetaccess (HSPA) channel. User equipment in the Cell_FACH state receivedata packets on a HS-DSCH instead of on the FACH. A HS-DSCH is a channelused in the high-speed downlink packet access (HSDPA) universal mobiletelecommunications system (UMTS) that sends packets on a downlink touser equipment. With enhanced Cell_FACH in the downlink, users in aCell_FACH state are allocated a HS-DSCH Radio Network TransactionIdentifier (H-RNTI). An H-RNTI is allocated by a controlling RNC (CRNC)when the user equipment establish a HS-DSCH channel, and is uniquewithin a cell carrying the HS-DSCH.

As described above, the E-RNTI is allocated by the base station whereasthe H-RNTI is allocated by the controlling RNC. Even if allocation ofE-RNTI in the base station has the advantage that the same nodeallocates the E-RNTI to users in both the Cell_FACH state and Cell_DCHstate, and thus guarantee uniqueness of E-RNTI in the cell, sucharrangements have several disadvantages. For example, such arrangementsdo not remove (or release) unused E-RNTIs allocated to Cell_FACH userequipment when required. Furthermore, as different nodes allocate theH-RNTI and the E-RNTI, the relation between a dedicated H-RNTI (e.g.,used for enhanced FACH) and the E-RNTI is unknown to the nodessupporting the user equipment using the E-DCH in the Cell_FACH state.The base station needs to know this relation for discontinuous reception(DRX) and other radio channel handling purpose.

SUMMARY

It is an object of the invention to overcome at least some of the abovedisadvantages, to enable a base station to remove (or release) unusedE-RNTIs, and to make the base station aware of a relation between uplinkand downlink channels for user equipment in the Cell_FACH state.

Embodiments described herein may solve the problems of releasing anallocated E-RNTI when the E-RNTI is no longer used by user equipment,and removing the released E-RNTI from a base station. For example, aradio network controller (e.g., based on signaling with user equipment)may know when the E-RNTI can be removed from the base station, and maytransmit a message (e.g., to the base station) providing an indicationthat the base station may remove the E-RNTI for use by other userequipment.

In an exemplary implementation of this embodiment, a device may includea memory to store a plurality of instructions, and a processing unit toexecute instructions in the memory to receive information regardingallocation of an enhanced dedicated channel radio network temporaryidentifier (E-RNTI) to user equipment in a cell forward access channel(Cell_FACH) state. The processing unit may further execute instructionsin the memory to receive information regarding a state change associatedwith the user equipment, determine that the E-RNTI can be released basedon the state change, and provide, to another device, a request torelease the E-RNTI in response to the state change and so that theE-RNTI can be used by other user equipment.

In another implementation of this embodiment, a method may beimplemented in a wireless environment that may include a first deviceand a second device, where the first device receives informationregarding cell access by user equipment in a cell forward access channel(Cell_FACH) state, and allocates an enhanced dedicated channel radionetwork temporary identifier (E-RNTI) for the user equipment in theCell_FACH state when the information regarding cell access is received.The method may include receiving, by the second device, informationregarding allocation of the E-RNTI to user equipment in the Cell_FACHstate, and receiving, by the second device, state information regardingsignaling between the user equipment and the second device. The methodmay also include providing, by the second device to the first device, arequest to release the E-RNTI in response to the state information andso that the E-RNTI can be used by other user equipment.

Another embodiment described herein may solve the problem of a basestation being unaware of a relation between uplink and downlink channelsfor user equipment in a Cell-FACH state. For example, a radio networkcontroller may provide both an allocated E-RNTI and an allocated H-RNTI(e.g., that provides temporary identities related to uplink and downlinkchannels) as information elements of a message transmitted to a basestation.

In an exemplary implementation of this embodiment, a system may includea base station to receive information regarding cell access by userequipment in a cell forward access channel (Cell_FACH) state, andallocate an enhanced dedicated channel radio network temporaryidentifier (E-RNTI) for the user equipment in the Cell_FACH state whenthe information regarding cell access is received. The system mayfurther include a radio network controller (RNC) to receive, from thebase station, a first message that includes the E-RNTI, generate asecond message that includes a dedicated high speed downlink sharedchannel radio network transaction identifier (H-RNTI) and the E-RNTI,and provide the second message to the base station.

In another implementation of this embodiment, a device may include amemory to store a plurality of instructions, and a processing unit toexecute instructions in the memory to receive information regarding cellaccess by user equipment in a cell forward access channel (Cell_FACH)state, and allocate an enhanced dedicated channel radio networktemporary identifier (E-RNTI) for the user equipment in the Cell_FACHstate when the information regarding cell access is received. Theprocessing unit may further execute instructions in the memory toprovide, to a radio network controller (RNC), a first message thatincludes the E-RNTI, and receive, from the radio network controller(RNC), a second message that includes a dedicated high speed downlinkshared channel radio network transaction identifier (H-RNTI) and theE-RNTI.

Embodiments described herein, after providing unique allocation of anE-RNTI for user equipment in a cell, may remove (or release) unusedE-RNTIs and may distribute the relation between a dedicated H-RNTI andthe E-RNTI to a base station that is controlling user equipment using anE-DCH in a Cell_FACH state. Furthermore, embodiments described hereinmay provide, to a base station, a relation between uplink and downlinkchannels for user equipment in the Cell_FACH state so that base stationis aware of the relation (e.g., for DRX and other radio channel handlingpurposes).

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a diagram of an exemplary network in which systems and/ormethods described herein may be implemented;

FIG. 2 illustrates a diagram of exemplary components of a base stationdepicted FIG. 1;

FIG. 3 depicts a diagram of exemplary components of a radio networkcontroller illustrated in FIG. 1;

FIG. 4 depicts a diagram of an exemplary E-RNTI allocation procedurecapable of being performed by components of an exemplary portion of thenetwork illustrated in FIG. 1;

FIG. 5 illustrates a diagram of an exemplary E-RNTI release procedurecapable of being performed by components of an exemplary portion of thenetwork depicted in FIG. 1;

FIGS. 6 and 7 depict diagrams of exemplary E-RNTI/H-RNTI messagingcapable of being provided by components of exemplary portions of thenetwork illustrated in FIG. 1;

FIG. 8 illustrates a flow chart of an exemplary process for releasing anE-RNTI according to embodiments described herein;

FIG. 9 depicts a flow chart of an exemplary process for removing anE-RNTI associated with inactive user equipment according to embodimentsdescribed herein; and

FIG. 10 illustrates a flow chart of an exemplary process for providingE-RNTI/H-RNTI messaging according to embodiments described herein.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements. Also, the following detailed description does notlimit the invention.

Embodiments described herein may enable a base station to remove (orrelease) unused E-RNTIs, and may enable a base station to become awareof a relation between uplink and downlink channels for user equipment inthe Cell_FACH state.

FIG. 1 depicts a diagram of an exemplary network 100 in which systemsand/or methods described herein may be implemented. As shown, network100 may include a group of user equipment (UE) 110-1 through 110-L(referred to collectively, and in some instances individually, as “userequipment 110”), a radio access network (RAN) 120, and a core network(CN) 130. Four pieces of user equipment 110, a single radio accessnetwork 120, and a single core network 130 have been illustrated in FIG.1 for simplicity. In practice, there may be more UEs 110, random accessnetworks 120, and/or core networks 130. Also, in some instances, acomponent in network 100 (e.g., one or more of user equipment 110, radioaccess network 120, and core network 130) may perform one or morefunctions described as being performed by another component or group ofcomponents in network 100.

User equipment 110 may include one or more devices capable ofsending/receiving voice and/or data to/from radio access network 120.User equipment 110 may include, for example, a radiotelephone, apersonal communications system (PCS) terminal (e.g., that may combine acellular radiotelephone with data processing and data communicationscapabilities), a personal digital assistant (PDA) (e.g., that caninclude a radiotelephone, a pager, Internet/intranet access, etc.), alaptop computer, etc.

Radio access network 120 may include one or more devices fortransmitting voice and/or data to user equipment 110 and core network130. As illustrated, radio access network 120 may include a group ofbase stations (BSs) 122-1 through 122-M (referred to collectively as“base stations 122” and in some instances, individually as “base station122”) and a group of radio network controllers (RNCs) 124-1 through124-N (referred to collectively as “radio network controllers 124” andin some instances, individually as “radio network controller 124”). Fourbase stations 122 and two radio network controllers 124 are shown inFIG. 1 for simplicity. In practice, there may be more or fewer basestations 122 and/or radio network controllers 124. Also, in someinstances, a component in radio access network 120 (e.g., one or more ofbase stations 122 and radio network controllers 124) may perform one ormore functions described as being performed by another component orgroup of components in radio access network 120.

Base stations 122 (also referred to as “Node Bs”) may include one ormore devices that receive voice and/or data from radio networkcontrollers 124 and transmit that voice and/or data to user equipment110 via an air interface. Base stations 122 may also include one or moredevices that receive voice and/or data from user equipment 110 over anair interface and transmit that voice and/or data to radio networkcontrollers 124 or other user equipment 110.

In one embodiment, base station 122 may receive information regardingcell access by user equipment 110 in a Cell_FACH state, and may allocatean E-RNTI for user equipment 110 in the Cell_FACH state when theinformation regarding cell access is received. Base station 122 mayprovide, to radio network controller 124, a first message that includesthe E-RNTI, and may receive, from radio network controller 124, a secondmessage that includes an H-RNTI and the E-RNTI.

Radio network controllers 124 may include one or more devices thatcontrol and manage base stations 122. Radio network controllers 124 mayalso include devices that perform data processing to manage utilizationof radio network services. Radio network controllers 124 maytransmit/receive voice and data to/from base stations 122, other radionetwork controllers 124, and/or core network 130.

A radio network controller 124 may act as a controlling radio networkcontroller (CRNC), a drift radio network controller (DRNC), or a servingradio network controller (SRNC). A CRNC may be responsible forcontrolling the resources of a base station 122. On the other hand, anSRNC may serve particular user equipment 110 and may manage connectionstowards that user equipment 110. Likewise, a DRNC may fulfill a similarrole to the SRNC (e.g., may route traffic between a SRNC and particularuser equipment 110).

As illustrated in FIG. 1, a radio network controller 124 may connect toa base station 122 via an Iub interface and to another radio networkcontroller 124 via an Iur interface.

In one embodiment, radio network controller 124 may receive informationregarding allocation of an E-RNTI to user equipment 110 in a Cell_FACHstate, and may receive information regarding a state change associatedwith user equipment 110. Radio network controller 124 may determine thatthe E-RNTI can be released based on the state change, and may provide,to base station 122, a request to release the E-RNTI in response to thestate change and so that the E-RNTI can be used by other user equipment110.

Core network 130 may include one or more devices that transfer/receivevoice and/or data to a circuit-switched and/or packet-switched network.In one embodiment, core network 130 may include, for example, a MobileSwitching Center (MSC), a Gateway MSC (GMSC), a Media Gateway (MGW), aServing General Packet Radio Service (GPRS) Support Node (SGSN), aGateway GPRS Support Node (GGSN), and/or other devices.

FIG. 2 illustrates a diagram of exemplary components of base station122. As shown in FIG. 2, base station 122 may include antennas 210,transceivers (TX/RX) 220, a processing system 230, and an Iub interface(I/F) 240.

Antennas 210 may include one or more directional and/or omni-directionalantennas. Transceivers 220 may be associated with antennas 210 and mayinclude transceiver circuitry for transmitting and/or receiving symbolsequences in a network, such as network 100, via antennas 210.

Processing system 230 may control the operation of base station 122.Processing system 230 may also process information received viatransceivers 220 and Iub interface 240. Processing system 230 mayfurther measure quality and strength of connection, may determine theframe error rate (FER), and may transmit this information to radionetwork controller 124. As illustrated, processing system 230 mayinclude a processing unit 232 and a memory 234.

Processing unit 232 may include one or more processors, microprocessors,application specific integrated circuits (ASICs), field programmablegate arrays (FPGAs), or the like. Processing unit 232 may processinformation received via transceivers 220 and Iub interface 240. Theprocessing may include, for example, data conversion, forward errorcorrection (FEC), rate adaptation, Wideband Code Division MultipleAccess (WCDMA) spreading/dispreading, quadrature phase shift keying(QPSK) modulation, etc. In addition, processing unit 232 may generatecontrol messages and/or data messages, and may cause those controlmessages and/or data messages to be transmitted via transceivers 220and/or Iub interface 240. Processing unit 232 may also process controlmessages and/or data messages received from transceivers 220 and/or Iubinterface 240.

Memory 234 may include a random access memory (RAM), a read-only memory(ROM), and/or another type of memory to store data and instructions thatmay be used by processing unit 232.

Iub interface 240 may include one or more line cards that allow basestation 122 to transmit data to and receive data from radio networkcontroller 124.

As described herein, base station 122 may perform certain operations inresponse to processing unit 232 executing software instructions of anapplication contained in a computer-readable medium, such as memory 234.A computer-readable medium may be defined as a physical or logicalmemory device. A logical memory device may include memory space within asingle physical memory device or spread across multiple physical memorydevices. The software instructions may be read into memory 234 fromanother computer-readable medium or from another device via antennas 210and transceivers 220. The software instructions contained in memory maycause processing unit 232 to perform processes described herein.Alternatively, hardwired circuitry may be used in place of or incombination with software instructions to implement processes describedherein. Thus, embodiments described herein are not limited to anyspecific combination of hardware circuitry and software.

Although FIG. 2 shows exemplary components of base station 122, in otherembodiments, base station 122 may contain fewer, different, differentlyarranged, or additional components than depicted in FIG. 2. In stillother embodiments, one or more components of base station 122 mayperform one or more other tasks described as being performed by one ormore other components of base station 122.

FIG. 3 depicts a diagram of exemplary components of radio networkcontroller 124. As shown, radio network controller 124 may include aprocessing system 310, an Iub interface 320, an Iur interface 330,and/or other interfaces 340.

Processing system 310 may control the operation of radio networkcontroller 124. As illustrated, processing system 310 may include aprocessing unit 312 and a memory 314. Processing unit 312 may handleprotocol exchanges between Iub interface 320, Iur interface 330, andother interfaces 340. In addition, processing unit 312 may generatecontrol messages and/or data messages and transmit those controlmessages and/or data messages via interfaces 320-340. Processing unit312 may also process control messages and/or data messages received frominterfaces 320-340. In one embodiment, processing unit 312 may includeone or more processors, microprocessors, application specific integratedcircuits (ASICs), field programmable gate arrays (FPGAs), or the like.Memory 314 may include a random access memory (RAM), a read-only memory(ROM), and/or another type of memory to store data and instructions thatmay be used by processing unit 212.

Iub interface 320 may include one or more line cards that allow radionetwork controller 124 to transmit control messages and/or data messagesto and receive control messages and/or data messages from base station122. Iur interface 330 may include one or more line cards that allowradio network controller 124 to transmit control messages and/or datamessages to and receive control messages and/or data messages fromanother radio network controller. Other interfaces 340 may includeinterfaces to other devices and/or networks. For example, otherinterfaces 340 may include an Iucs interface, which is a core networkinterface to a circuit-switched voice network, and an Iups interface,which is a core network interface to a packet-switched data network.

As described herein, radio network controller 124 may perform certainoperations in response to processing unit 312 executing softwareinstructions of an application contained in a computer-readable medium,such as memory 314. The software instructions may be read into memory314 from another computer-readable medium or from another device. Thesoftware instructions contained in memory may cause processing unit 312to perform processes described herein. Alternatively, hardwiredcircuitry may be used in place of or in combination with softwareinstructions to implement processes described herein. Thus, embodimentsdescribed herein are not limited to any specific combination of hardwarecircuitry and software.

Although FIG. 3 shows exemplary components of radio network controller124, in other embodiments, radio network controller 124 may containfewer, different, differently arranged, or additional components thandepicted in FIG. 3. In still other embodiments, one or more componentsof radio network controller 124 may perform one or more other tasksdescribed as being performed by one or more other components of radionetwork controller 124.

FIG. 4 depicts a diagram of an exemplary E-RNTI allocation procedurecapable of being performed by components of an exemplary portion 400 ofnetwork 100. As shown, exemplary network portion 400 may include userequipment 110-1, user equipment 110-2, base station 122-1, and RNC124-1. User equipment 110-1 and 110-2 may include the features describedabove in connection with, for example, FIG. 1. Base station 122-1 mayinclude the features described above in connection with, for example,FIGS. 1 and 2. RNC 124-1 may include the features described above inconnection with, for example, FIGS. 1 and 3.

As further shown in FIG. 4, user equipment 110-1 may be in a Cell_DCHstate 410, and base station 122-1 may allocate an E-RNTI 420 for userequipment 110-1 in Cell-DCH state 410. Base station 122-1 may inform(e.g., via node B application part (NBAP) and/or radio network subsystemapplication part (RNSAP) radio link dedicated signaling) RNC 124-1 aboutallocated E-RNTI 420. For example, base station 122-1 may inform RNC124-1 about E-RNTI 420 in a response message associated with a dedicatedradio link procedure that sets up this serving radio link. After basestation 122-1 informs RNC 124-1 about E-RNTI 420, RNC 124-1 may informuser equipment 110-1 about E-RNTI 420, via radio resource control (RRC)signaling 430. Such a procedure may not be applicable when userequipment is in a Cell_FACH state since there may be no dedicated radiolink-related signaling over Iub and Iur.

User equipment 110-2 may be in a Cell-FACH state 440 and E-RNTIsallocated for user equipment 110-1 and user equipment 110-2 may beunique within a cell. Thus, base station 122-1 may allocate the E-RNTIsregardless of a state associated with user equipment. For backwardscompatibility purposes, base station 122-1 may allocate E-RNTIs for userequipment in the Cell_FACH state, such as user equipment 110-2. Whenuser equipment 110-2 accesses a new cell on the CCCH for an E-DCH in theCell_FACH state (e.g., via a cell update, a UTRAN Registration Area(URA) update, a RRC connection request, etc.), as indicated by referencenumber 450, base station 122-1 may allocate an E-RNTI 460 for userequipment 110-2. Base station 122-1 may inform RNC 124-1 about allocatedE-RNTI 460. After base station 122-1 informs RNC 124-1 about E-RNTI 460,RNC 124-1 may inform user equipment 110-2 about E-RNTI 460, via RRCsignaling 470 (e.g., in a RRC response message to a RRC initiatingmessage).

RRC messages sent in the uplink on the CCCH may be transported in an Iubframing protocol to RNC 124-1 (e.g., a MAC-c termination point) andthereafter may be forwarded using a RNSAP uplink signaling transferindication message. In one example, base station 122-1 may includeE-RNTI 460 in an Iub frame of the Iub framing protocol when an uplinkmessage on the CCCH for the E-DCH in the CELL_FACH state is received,and may include E-RNTI 460 in a new information element of the RNSAPuplink signaling transfer indication message. Instead of using the Iubframing protocol to inform RNC 124-1 about E-RNTI 460, base station122-1 may invoke a new NBAP procedure and may send information aboutE-RNTI 460 to RNC 124-1 in the control plane. The NBAP procedure mayinclude a binding to the frame sent in the user plane with a first RRCmessage.

Segmentation of the CCCH may be considered when defining the layout ofthe Iub frame (or frames) that carries the CCCH. Base station 122-1 maynot differentiate a CCCH for an E-DCH in a Cell_FACH frame carrying aRRC cell update message from a frame carrying a RRC connection request.Therefore, E-RNTI 460 may need to be included in a first uplink Iubframe when the CCCH for the E-DCH in the Cell_FACH state is used, evenif the radio network subsystem reconfigures idle user equipment to aCell_DCH state when user equipment 110-2 requests an RRC connection. Forbackwards compatibility purposes, E-RNTI 460 may be included in a radiolink setup response if RNC 124-1 decides to change a state of userequipment 110-2 to a Cell_DCH state and base station 122-1 receives aradio link setup request.

Although FIG. 4 shows exemplary components of network portion 400, inother embodiments, network portion 400 may contain fewer, different,differently arranged, or additional components than depicted in FIG. 4.In still other embodiments, one or more components of network portion400 may perform one or more other tasks described as being performed byone or more other components of network portion 400.

FIG. 5 illustrates a diagram of an exemplary E-RNTI release procedurecapable of being performed by components of an exemplary portion 500 ofnetwork 100. As shown, exemplary network portion 500 may include userequipment 110-2, base station 122-1, and RNC 124-1. User equipment 110-2may include the features described above in connection with, forexample, FIG. 1. Base station 122-1 may include the features describedabove in connection with, for example, FIGS. 1 and 2. RNC 124-1 mayinclude the features described above in connection with, for example,FIGS. 1 and 3.

Base station 122-1 may not be aware of status changes associated withuser equipment 110-2 since base station 122-1 may not terminate RRCsignaling and may not be in contact with RNC 124-1 via RNSAP commontransport channel procedures. For example, if user equipment 110-2leaves a cell and/or goes idle, as indicated by reference number 510,base station 122-1 may not be aware that user equipment 110-2 leavescell/goes idle 510. RNC 124-1 may be made aware of status changes (e.g.,leaves cell/goes idle 510) associated with user equipment 110-2, via UEstate change information 520. UE state change information 520 mayinclude status information associated with user equipment 110-2.

An E-RNTI associated with user equipment 110-2 may need to be unique ina cell. If user equipment 110-2 is no longer in the Cell_FACH, URA_PCH,and/or Cell_PCH states, the E-RNTI associated with user equipment 110-2may be unused (or “hanging”) and may need to be released. RNC 124-1 mayinform base station 122-1 of any status change for user equipment 110-2that implies that an E-RNTI should be released. For example, if RNC124-1 determines that the E-RNTI associated with user equipment 110-2should be released, RNC 124-1 may initiate an E-RNTI release request530, and may provide E-RNTI release request 530 to base station 122-1.If RNC 124-1 is a CRNC triggered by common transport channel procedures,RNC 124-1 may invoke a new common NBAP procedure or may send a new Iubframing protocol control frame to inform base station 122-1 that theE-RNTI associated with user equipment 110-2 should be released. If RNC124-1 is a SRNC, RNC 124-1 may use new common procedures on RNSAP and/orNBAP to inform base station 122-1 that the E-RNTI associated with userequipment 110-2 should be released. For example, RNC 124-1 may implementa new common class “2” procedure on RNSAP, or may reuse an existingprocedure (e.g., information exchange initiation/termination proceduresor other suitable common procedures). An E-RNTI may be a hanging (e.g.,not released) E-RNTI when base station 122-1 does not receive anacknowledgement that the E-RNTI associated with user equipment 110-2should be released.

When base station 122-1 receives E-RNTI release request 530, basestation 122-1 may remove the E-RNTI for user equipment 110-2 in thecell, as indicated by reference number 540, and may (optionally) providean acknowledgement of the release of the E-RNTI to RNC 124-1, asindicated by reference number 550.

If RNC 124-1 utilizes the class “1” or class “2” procedure describedabove, a lost downlink NBAP class “2” message may provide an indicationof a “hanging” E-RNTI. This may be solved with a periodic cleanup. Forexample, as shown in FIG. 5, if base station 122-1 determines that userequipment 110-2 has been inactive (e.g., longer than a time thresholdand/or longer than another threshold defining a number of inactive userequipment in the cell), base station 122-1 may provide an indication 560of user equipment 110-2 inactivity to an operations and maintenance(O&M) system. If user equipment 110-2 has been inactive for longer thanone of the thresholds, the O&M system may initiate a cleanup procedure570 via base station 122-1. Cleanup procedure 570 may instruct basestation 122-1 to directly remove the E-RNTI associated with userequipment 110-2. In one example, the thresholds may take intoconsideration a situation where user equipment in the Cell_PCH state isinactive for a very long time (e.g., hours, days, or even longer).

As described above, base station 122-1 may be not aware of when userequipment leaves the cell, goes to idle mode, or no longer uses theE-RNTI. Since base station 122-1 informs RNC 124-1 about the E-RNTI foruser equipment 110-2, RNC 124-1 knows to which user equipment an E-RNTIis allocated and thus which user equipment need to be monitored forstatus changes. In one embodiment, RNC 124-1, via NBAP, may send a userequipment status update to base station 122-1 when user equipment 110-2(e.g., with an allocated E-RNTI) changes its state to idle mode, leavesthe cell, or if RNC 124-1 decides that user equipment 110-2 may nolonger use the E-DCH channel in Cell_FACH state.

Before RNC 124-1 requests base station 122-1 to remove an E-RNTI foruser equipment 11-02, RNC 124-1 may inform user equipment 110-2 not touse the E-RNTI (e.g., via RRC signaling) RNC 124-1 may use the followingprocedure to inform base station 122-1 that user equipment 110-2 may nolonger use an allocated E-RNTI for uplink transport on E-DCH inCell_FACH state. RNC 124-1 may send a UE status update message to basestation 122-1. Upon reception of the UE status update message, basestation 122-1 may remove user equipment's 110-2 association with theE-RNTI, and may release the allocated E-RNTI. When the E-RNTI isreleased, base station 122-1 may respond with a UE status updateresponse message to RNC 124-1. Table 1 illustrates an example of a UEstatus update message format in the NBAP protocol.

TABLE 1 IE Type IE/Group and Semantics Assigned Name Presence RangeReference Description Criticality Criticality Message M 9.2.1.45 —Discriminator Message Type M 9.2.1.46 YES reject Transaction ID M9.2.1.62 — Cell E-RNTI 1 . . . <maxCellinNodeB> Status Information >C-ID M 9.2.1.9 > Vacant E- 1 . . . <maxErntiToRelease> RNTI >> E-RNTI M9.2.1.75

Although FIG. 5 shows exemplary components of network portion 500, inother embodiments, network portion 500 may contain fewer, different,differently arranged, or additional components than depicted in FIG. 5.In still other embodiments, one or more components of network portion500 may perform one or more other tasks described as being performed byone or more other components of network portion 500.

FIG. 6 depicts a diagram of exemplary E-RNTI/H-RNTI messaging capable ofbeing provided by components of an exemplary portion 600 of network 100.As shown, exemplary network portion 600 may include user equipment110-2, base station 122-1, RNC 124-1, and RNC 124-N. User equipment110-2 may include the features described above in connection with, forexample, FIG. 1. Base station 122-1 may include the features describedabove in connection with, for example, FIGS. 1 and 2. RNC 124-1 and124-N may include the features described above in connection with, forexample, FIGS. 1 and 3. It may be assumed that RNC 124-1 is a CRNCand/or a DRNC, and that RNC 124-N is a SRNC.

There may be a need for base station 122-1 to know which dedicatedH-RNTI is allocated to user equipment (e.g., user equipment 110-2) usingthe enhanced uplink in the Cell_FACH state. Base station 122-1 may needto know which dedicated H-RNTI is allocated to user equipment 110-2before user equipment 110-2 attempts to access the E-DCH in theCell_FACH state using the DTCH/DCCH and E-RNTI contention resolution.

As shown in FIG. 6, user equipment 110-2 may provide a first message 610to base station 122-1 on the CCCH. First message 610 may include, forexample, a RRC message. Base station 122-1 may forward the content offirst message 610, in a second message 620 (e.g., an Iub frame), to RNC124-1. Second message 620 may include an E-RNTI (e.g., E-RNTI 460 (FIG.4)) allocated to user equipment 110-2 (e.g., when user equipment 110-2accesses a new cell) and the RRC message contained in first message 610.When RNC 124-1 receives second message 620 (e.g., and the E-RNTI and theRRC message contained in first message 610), RNC 124-1 may provide, toRNC 124-N, a message 630 (e.g., that includes a dedicated H-RNTIallocated to user equipment 110-2), the E-RNTI, and the RRC messagecontained in first message 610. Message 630 may include a RNSAP uplinksignaling transfer indication message (e.g., in case of Iur). RNC 124-Nmay provide, to RNC 124-1, a RNSAP message 640 (e.g., using RNSAPdownlink signaling transfer indication) that includes a RRC messageresponse, the dedicated H-RNTI, and the E-RNTI. RNC 124-1 may provide,to base station 122-1, a message 650 that includes the RRC messageresponse in one field, the dedicated H-RNTI in another field, and theE-RNTI in still another field. Base station 122-1 may receive message650, and may provide a RRC message response 660 (e.g., the RRC messageresponse contained in message 650) to user equipment 110-2. RRC messageresponse 660 may include the dedicated H-RNTI and the E-RNTI. When userequipment 110-2 receives RRC message response 660, user equipment 110-2may attempt to access the E-DCH in the Cell_FACH state using theDTCH/DCCH and E-RNTI contention resolution.

However, before the E-RNTI is allocated to user equipment 110-2, userequipment 110-2 may access the E-DCH in the Cell_FACH state using theCCCH. FIG. 7 depicts when and where the E-RNTI and the dedicated H-RNTIare allocated in such a situation. FIG. 7 depicts a diagram of exemplaryE-RNTI/H-RNTI messaging capable of being provided by components of anexemplary portion 700 of network 100. As shown, exemplary networkportion 700 may include user equipment 110-2, base station 122-1, RNC124-1, and RNC 124-N. User equipment 110-2 may include the featuresdescribed above in connection with, for example, FIG. 1. Base station122-1 may include the features described above in connection with, forexample, FIGS. 1 and 2. RNC 124-1 and 124-N may include the featuresdescribed above in connection with, for example, FIGS. 1 and 3. It maybe assumed that RNC 124-1 is a CRNC and/or a DRNC, and that RNC 124-N isa SRNC.

As further shown in FIG. 7, a random access channel (RACH) (e.g., anuplink transport channel) procedure 705 may be conducted between userequipment 110-2 and base station 122-1. In one example, RACH procedure705 may include user equipment 110-2 decoding a broadcast controlchannel (BCH) (e.g., to determine available RACH sub-channels,scrambling codes, and signatures), and selecting one of the RACHsub-channels and one of the signatures. User equipment 110-2 may measurea downlink power level, may set an initial RACH power level, may send aRACH preamble to base station 122-1, and may decode the acquisitionindicator channel (AICH) to determine whether base station 122-1detected the RACH preamble. If no AICH transmission is detected, userequipment 110-2 may increase the RACH preamble transmission power, andmay retransmit the RACH preamble to base station 122-1. When an AICHtransmission is detected from base station 122-1, user equipment 110-2may transmit a message part of the RACH transmission.

An uplink synchronization procedure 710 may be conducted between userequipment 110-2 and base station 122-1. Uplink synchronization procedure710 may include base station 122-1 monitoring signals from userequipment 110-2, and making timing adjustments in the transmission basedon the monitored signals.

As further shown in FIG. 7, if user equipment 110-2 attempts to accessthe E-DCH on the CCCH, as indicated by reference number 715, basestation 122-1 may allocate an E-RNTI for user equipment 110-2, asindicated by reference number 720. After allocating the E-RNTI for userequipment 110-2, base station 122-1 may provide a first message 725(that includes a first RRC message received from user equipment 110-2),via the Iub framing protocol (FP), to RNC 124-1. First message 725 mayinclude the E-RNTI allocated to user equipment 110-2. When RNC 124-1receives first message 725 (e.g., the first RRC message and the E-RNTI),RNC 124-1 may allocate a dedicated H-RNTI for user equipment 110-2, asindicated by reference number 730, and may provide an uplink signalingtransfer indication message 735 to RNC 124-N. Uplink signaling transferindication message 735 may include the first RRC message, the allocatedE-RNTI, and the dedicated H-RNTI.

RNC 124-N may receive uplink signaling transfer indication message 735,and may provide a downlink signaling transfer indication message 740 toRNC 124-1. Downlink signaling transfer indication message 740 mayinclude a RRC message response, the allocated E-RNTI, and the dedicatedH-RNTI. In one embodiment, messages 735 and 740 may be provided betweenRNC 124-1 and RNC 124-N via a RNSAP common transport channel 745. RNC124-1 may receive downlink signaling transfer indication message 740,and may provide a message 750 (e.g., “HS-DSCH DATA FRAME<Common-H-RNTI>, <RRCmessage resp>, <E-RNTI>, <dedicated H-RNTI>”) tobase station 122-1, via the Iub framing protocol (FP). As shown, message750 may include the RRC message response, the allocated E-RNTI, thededicated H-RNTI, and other information. Base station 122-1 may receivemessage 750, and may provide a message 755 (e.g., that includes the RRCmessage response, the allocated E-RNTI, and the dedicated H-RNTI) touser equipment 110-2, via enhanced FACH on the CCCH. User equipment110-2 may receive message 755, and may start a first contentionresolution on the DCCH/DTCH based on the allocated E-RNTI, as indicatedby reference number 760.

If the dedicated H-RNTI is sent in a procedure that is independent ofthe downlink RRC message response, a race condition may occur betweenreception of the dedicated H-RNTI in base station 122-1 via thisindependent procedure and reception of the RRC response message by userequipment 110-2. With an independent procedure there may be a risk thatbase station 122-1 has not received the relation between the allocatedE-RNTI and the dedicated H-RNTI at the start of the first contentionresolution (e.g., by user equipment 110-2). A consequence of this mayinclude disturbance in a discontinuous reception (DRX) procedure thatresults in a lost frame.

However, such a race condition may be avoided. For example, it may beassumed that a NBAP (or Iub) framing protocol control message is theindependent procedure that may generate a race condition. If a header ofthe Iub frame carrying the RRC message response is used, the racecondition may be avoided. The H-RNTI (e.g., a common H-RNTI) to be usedover the downlink may be included in message 750 (e.g., the HS-DSCH DATAFRAME TYPE 2 message). If the dedicated H-RNTI and the allocated E-RNTIare included in message 750 (e.g., in spare extensions of message 750),base station 122-1 may associate the allocated E-RNTI with the dedicatedH-RNTI. Thus, the dedicated H-RNTI may be carried both in RRC messages(e.g., as a payload of the framing protocol frame) and in a frameprotocol header. The allocated E-RNTI and the dedicated H-RNTI may beincluded if user equipment 110-2 will be in a Cell_FACH, URA_PCH, and/orCell_PCH states after completion of the RRC procedure. In other words,if the downlink RRC message reconfigures user equipment 110-2 to theCell_DCH, then the allocated E-RNTI and the dedicated H-RNTI may not beincluded.

In one embodiment, the NBAP class “2” procedure described above inconnection with FIG. 5 may be used to inform base station 122-1 aboutthe allocated H-RNTI. Depending on the selected method for DRX and otherLayer 2 handling of the E-DCH in the Cell_FACH state, lack of awarenessof the dedicated H-RNTI in base station 122-1, at the first contentionresolution (e.g., based on the E-RNTI) may be acceptable. If so, theNBAP class “2” procedure may be selected.

If RNC 124-1 changes the dedicated H-RNTI to a new H-RNTI, the newdedicated H-RNTI may be associated with a downlink RRC message thatinforms user equipment 110-2 about the new dedicated H-RNTI. RNC 124-1may include new information elements (e.g., the E-RNTI and the newdedicated H-RNTI) in a header of the Iub frame and base station 122-1may check the Iub frame header when user equipment 110-2 is using theDTCH/DCCH. In another embodiment, when RNC 124-1 changes the dedicatedH-RNTI, base station 122-1 may be informed about the new dedicatedH-RNTI using, for example, a NBAP message UE status indication message.

RNC 124-1 may send information to base station 122-1 about whichdedicated H-RNTI is allocated to user equipment 110-2, and userequipment 110-2 may be identified by the E-RNTI. Either NBAP or Iubframing protocol may be used depending on the selected method for DRXand other Layer 2 handling of the E-DCH in the Cell_FACH state. Forexample, a downlink Iub frame may carry a RRC message that sends a newor changed dedicated H-RNTI to user equipment in the Cell_FACH, URA_PCH,and/or Cell_PCH states, with enhanced RACH. The Iub frame protocolheader may include the new dedicated H-RNTI as well as the E-RNTIallocated to the user equipment. In another example, an NBAP class “2”procedure may be used to signal the new dedicated H-RNTI as well as theE-RNTI allocated to user equipment 110-2. Alternatively and/oradditionally, a NBAP class “1” procedure may be used to inform basestation 122-1 about the allocated H-RNTI. An acknowledgement may be sentfrom base station 122-1 to RNC 124-1. Therefore, RNC 124-1 can supervisethe reception of the new dedicated H-RNTI, and the risk of lost NBAPmessages may be eliminated.

Although FIGS. 6 and 7 show exemplary components of network portions 600and 700, in other embodiments, network portions 600 and 700 may containfewer, different, differently arranged, or additional components thandepicted in FIGS. 6 and 7. In still other embodiments, one or morecomponents of network portions 600 and 700 may perform one or more othertasks described as being performed by one or more other components ofnetwork portions 600 and 700.

FIG. 8 depicts a flow chart of an exemplary process 800 for releasing anE-RNTI according to embodiments described herein. In one embodiment,process 800 may be performed by base station 122-1 and RNC 124-1. Inother embodiments, some or all of process 800 may be performed by basestation 122-1 and RNC 124-1 in combination with another device or groupof devices (e.g., communicating with base station 122-1 and RNC 124-1).

As illustrated in FIG. 8, process 800 may include identifying, via RNC124-1, a state change for user equipment in the Cell_FACH or Cell_PCHstate (block 810), and initiating, via RNC 124-1, a release request foran E-RNTI associated with the user equipment (block 820). For example,in embodiments described above in connection with FIG. 5, RNC 124-1 maybe made aware of status changes (e.g., leaves cell/goes idle 510)associated with user equipment 110-2, via UE state change information520. RNC 124-1 may inform base station 122-1 of any status change foruser equipment 110-2 that implies that an E-RNTI should be released. Inone example, if RNC 124-1 determines that the E-RNTI associated withuser equipment 110-2 should be released, RNC 124-1 may initiate anE-RNTI release request 530, and may provide E-RNTI release request 530to base station 122-1.

Returning to FIG. 8, base station 122-1 may release the E-RNTIassociated with the user equipment in the Cell_FACH or Cell_PCH state(block 830), base station 122-1 may (optionally) acknowledge release ofthe E-RNTI associated with the user equipment (block 840), and RNC 124-1may (optionally) receive acknowledgement of the E-RNTI release (block850). For example, in embodiments described above in connection withFIG. 5, when base station 122-1 receives E-RNTI release request 530,base station 122-1 may remove the E-RNTI for user equipment 110-2 in thecell, as indicated by reference number 540, and may (optionally) providean acknowledgement of the release of the E-RNTI to RNC 124-1, asindicated by reference number 550.

FIG. 9 illustrates a flow chart of an exemplary process 900 for removingan E-RNTI associated with inactive user equipment according toembodiments described herein. In one embodiment, process 900 may beperformed by base station 122-1. In other embodiments, some or all ofprocess 900 may be performed by base station 122-1 in combination withanother device or group of devices (e.g., communicating with basestation 122-1).

As illustrated in FIG. 9, process 900 may include determining that userequipment in a Cell-FACH state is inactive (block 910), and providing anindication of the inactive user equipment to an operations andmaintenance (O&M) system, where the O&M system initiates a cleanupprocedure to remove the E-RNTI associated with the inactive userequipment (block 920). For example, in embodiments described above inconnection with FIG. 5, if base station 122-1 determines that userequipment 110-2 has been inactive (e.g., longer than a time thresholdand/or longer than another threshold defining a number of inactive userequipments in the cell), base station 122-1 may provide indication 560of user equipment 110-2 inactivity to an operations and maintenance(O&M) system. If user equipment 110-2 has been inactive for longer thanone of the thresholds, the O&M system may initiate cleanup procedure 570via base station 122-1. Cleanup procedure 570 may instruct base station122-1 to directly remove the E-RNTI associated with user equipment110-2.

FIG. 10 depicts a flow chart of an exemplary process 1000 for providingE-RNTI/H-RNTI messaging according to embodiments described herein. Inone embodiment, process 1000 may be performed by base station 122-1 andRNC 124-1. In other embodiments, some or all of process 1000 may beperformed by base station 122-1 and RNC 124-1 in combination withanother device or group of devices (e.g., communicating with basestation 122-1 and RNC 124-1).

As illustrated in FIG. 10, process 1000 may include receiving, via basestation 122-1, a first message from user equipment in an idle,Cell-FACH, URA_PCH, and/or Cell_PCH state (block 1010), providing, viabase station 122-1, a second message (that includes an E-RNTI and an RRCmessage received via the first message) to RNC 124-1 (block 1020), andreceiving, via RNC 124-1, the second RRC message (block 1030). Forexample, in embodiments described above in connection with FIG. 6, userequipment 110-2 may provide first message 610 to base station 122-1 onthe CCCH. First message 610 may include, for example, a RRC message.Base station 122-1 may forward the content of first message 610, insecond message 620 (e.g., an Iub frame), to RNC 124-1. Second message620 may include an E-RNTI (e.g., E-RNTI 460 (FIG. 4)) allocated to userequipment 110-2 (e.g., when user equipment 110-2 accesses a new cell)and the RRC message contained in first message 610.

Returning to FIG. 10, RNC 124-1 may provide, to a SRNC, a message (thatincludes a dedicated H-RNTI for enhanced Cell_FACH, the E-RNTI, and theRRC message) (block 1040), may receive a RNSAP message (that includes aRRC message response, the E-RNTI, and the dedicated H-RNTI) from theSRNC (block 1050), and may provide a message (that includes the RRCmessage response, the E-RNTI, and the dedicated H-RNTI) to base station122-1 (block 1060). For example, in embodiments described above inconnection with FIG. 6, when RNC 124-1 receives second message 620(e.g., and the E-RNTI and the RRC message contained in first message610), RNC 124-1 may provide, to RNC 124-N, message 630 (e.g., thatincludes a dedicated H-RNTI allocated to user equipment 110-2), theE-RNTI, and the RRC message contained in first message 610. Message 630may include a RNSAP uplink signaling transfer indication message (e.g.,in case of Iur). RNC 124-N may provide, to RNC 124-1, RNSAP message 640(e.g., using RNSAP downlink signaling transfer indication) that includesa RRC message response, the dedicated H-RNTI, and the E-RNTI. RNC 124-1may provide, to base station 122-1, message 650 that includes the RRCmessage response in one field, the dedicated H-RNTI in another field,and the E-RNTI in still another field.

As further shown in FIG. 10, base station 122-1 may receive the message(that includes the RRC message response, the E-RNTI, and the dedicatedH-RNTI) from RNC 124-1 (block 1070), and may provide the RRC messageresponse to the user equipment (block 1080). For example, in embodimentsdescribed above in connection with FIG. 6, base station 122-1 mayreceive message 650, and may provide RRC message response 660 (e.g., theRRC message response contained in message 650) to user equipment 110-2.RRC message response 660 may include the dedicated H-RNTI and theE-RNTI. When user equipment 110-2 receives RRC message response 660,user equipment 110-2 may attempt to access the E-DCH in the Cell_FACHstate using the DTCH/DCCH and E-RNTI contention resolution.

Embodiments described herein may enable a base station to remove (orrelease) unused E-RNTIs, and may enable a base station to become awareof a relation between uplink and downlink channels for user equipment inthe Cell_FACH state. Embodiments described herein, after providingunique allocation of an E-RNTI for user equipment in a cell, may remove(or release) unused E-RNTIs and may distribute the relation between adedicated H-RNTI and the E-RNTI to a base station that is controllinguser equipment using an E-DCH in a Cell_FACH state. Furthermore,embodiments described herein may provide, to a base station, a relationbetween uplink and downlink channels for user equipment in the Cell_FACHstate so that base station is aware of the relation (e.g., for DRX andother radio channel handling purposes).

Embodiments described herein provide illustration and description, butare not intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above teachings, or may be acquired from practice of theimplementations. For example, while series of blocks have been describedwith regard to FIGS. 8-10, the order of the blocks may be modified inother embodiments. Further, non-dependent blocks may be performed inparallel.

The exemplary embodiments, as described above, may be implemented inmany different forms of software, firmware, and hardware in theimplementations illustrated in the figures. The actual software code orspecialized control hardware used to implement the exemplary embodimentsdescribed herein is not limiting of the invention. Thus, the operationand behavior of the exemplary embodiments were described withoutreference to the specific software code—it being understood that onewould be able to design software and control hardware to implement theexemplary embodiments based on the description herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the invention. In fact, many of these features may becombined in ways not specifically recited in the claims and/or disclosedin the specification.

It should be emphasized that the terms “comprises/comprising” when usedin the this specification are taken to specify the presence of statedfeatures, integers, steps, or components, but do not preclude thepresence or addition of one or more other features, integers, steps,components, or groups thereof.

No element, act, or instruction used in the description of the presentapplication should be construed as critical or essential to theinvention unless explicitly described as such. Also, as used herein, thearticle “a” is intended to include one or more items. Where only oneitem is intended, the term “one” or similar language is used. Further,the phrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A radio network controller (RNC) devicecomprising: a processor that operates to: receive information regardingallocation of an enhanced dedicated channel radio network temporaryidentifier (E-RNTI) to user equipment in a cell forward access channel(Cell_FACH) state; generate a message that includes a high speeddownlink shared channel radio network transaction identifier (H-RNTI)and the E-RNTI; and provide the message to the base station.
 2. Thedevice of claim 1, where the H-RNTI is a peer of the E-RNTI.
 3. A methodperformed in a radio network controller in a wireless environment, theradio network controller being connected to a base station, the methodcomprising the steps of: receiving information, regarding allocation ofan enhanced dedicated channel radio network temporary identifier(E-RNTI) to user equipment in a cell forward access channel (Cell_FACH)state from the base station; generating a message that includes adedicated high speed downlink shared channel radio network transactionidentifier (H-RNTI) and the E-RNTI; and providing the message to thebase station.
 4. The method of claim 3, wherein the informationregarding allocation of the E-RNTI to the user equipment in theCell_FACH state is forwarded to the radio network controller by the basestation in a second message.
 5. The method of claim 3, furthercomprising: providing the message to the base station using a Node Bapplication part (NBAP) or an Iub data frame.
 6. The method of claim 3,wherein the H-RNTI is a peer of the E-RNTI.
 7. A base stationcomprising: a processor that operates to: receive information regardingcell access by user equipment in a cell forward access channel(Cell_FACH) state; allocate an enhanced dedicated channel radio networktemporary identifier (E-RNTI) for the user equipment in the Cell_FACHstate when the information regarding cell access is received; provide toa radio network controller (RNC) a first message that includes theE-RNTI; and receive, from the RNC, a second message that includes adedicated high speed downlink shared channel radio network transactionidentifier (H-RNTI) and the E-RNTI.